| name | explain-diff-html |
|---|---|
| description | Use when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces HTML output. |
Please make me a rich, interactive explanation of the specified code change.
It should have these sections:
Discover gists
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
| name | bikeshed |
|---|---|
| description | Run two independent subagents through a structured debate on the same prompt — independent answers, cross-critique, revision, then a synthesized unified response. Use when explicitly invoked as /bikeshed with a prompt, or when the user asks for a two-agent debate/adversarial comparison on a plan, design, or other complex piece of work. Best for plans and complex open-ended work, not simple factual questions. |
Take the user's prompt (everything after /bikeshed), run it through two independent subagents in a debate protocol, and synthesize their final answers into one unified response. If no prompt was given, ask the user what question or plan to bikeshed before starting.
The value comes from independence followed by controlled exchange. Do not let either agent see the other's work before Round 1 is complete, and do not editorialize when relaying material between them — pass responses and critiques verbatim.
Native Home Assistant control of an XGIMI Titan Noir / Titan Noir Max projector over its USB-to-RS232 serial interface, using a cheap ESP32. The Titan Noir has no shipping IP control, but serial works — including power-on from standby, which BLE and CEC can't do dependably.
Before you invest time in this: it's a tinkerer's project (an ESP32, a USB-serial cable, a few jumper wires, ESPHome) — and there's one projector quirk that trips everyone up. Read The catch below first. Depending on your
The brand new 2020 exam (I got mine on aug. 2020) is slightly different to what it used to be.
The online courses that I have followed (A Cloud Guru & Linux Academy) were presenting a 50 questions exam running over a 90 minutes timeframe.
The new exam is only 28 questions within a 60 minutes timeframe. That's shorter with probably slightly less answers. Probably because the exam explains clearly that every answer in the multiple choice questions are worth one point. I didn't took the time to count the exact number of answers but I tend to think it was slightly above 40.
-
Download lastest Android platform tools
-
Unzip the folder to
platform-tools- Use ADB with
./platformtools/adb <COMMAND>
- Use ADB with
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Cheat Sheet | |
| import warnings | |
| warnings.filterwarnings('ignore') | |
| # Pandas | |
| pd.to_numeric(df, coalesce="") | |
| pd.to_datetime() | |
| pd.to_timestamp() | |
| pd.to_timedelta() |
| name | cognitive-rhythm-writing |
|---|---|
| description | 説明的な文章に緩急を設計するための規範。緩急を装飾ではなく認知モードの切替（観察→逡巡→断定→再観察）と未回収の緊張の管理として扱い、文の拍、段落の密度波形、節の入り方、緩みと駄文の判別、執筆後の機械的な点検手順を定める。読み物として読ませたい章・記事・解説文を生成するとき、または「密度はあるが平坦でおもしろくない」文章を診断・修正するときに使用する。 |
密度の高い文章が退屈になるのは、情報が多いからではなく、全文が同じ認知モードで書かれているからである。 この規範は、読者の認知モード（観察する、迷う、確信する、確かめ直す）を意図的に切り替え、常に「続きを読む理由」を維持することで、読み進める推進力を作る。
tdcosta100
/ WSL2GUIWSLg-XWayland-en.md
Last active
July 26, 2026 01:31
A tutorial to use GUI in WSL2/WSLg replacing original Xorg by Xwayland, allowing WSL to work like native Linux, including login screen
Note
If you want to use Wayland in WSLg in a simpler setup, you can try the WSLg (Wayland) tutorial.
In this tutorial, we will setup GUI in WSL2. No additional software outside WSL (like VcXsrv or GWSL) is required. You will find this tutorial very similar to the one that replaces Xorg with Xvnc. Indeed, it's pretty much the same tutorial, with some few changes.
The key component we need to install is the desktop metapackage you want (GNOME, KDE, Xfce, Budgie, etc), and after that, replace the default Xorg by a script that calls Xwayland instead.
For this setup, I will use Ubuntu 24.04, and install GNOME Desktop. Unfortunately older versions of Ubuntu lack some fundamental things, so we cannot reproduce it in older versions (at least not fully). Since the key components aren't bound to Ubuntu or GNOME, you can use your favorite distro and GUI. Check the [Sample screenshot
Caution
As of April 7th 2026, Discord has expressed their intent to crack down on automating quest completion.
Some users have received the following system message:
There isn't much I can do to make the script undetected, so use it at your own risk, as you most likely WILL get flagged by doing so.
NewerOlder